Skip to content

Conversation

@CoelacanthusHex
Copy link

Metric-compatible font with Times New Roman created by ParaType, based on their serif font PT Serif, released under OFL-1.1 license.

https://www.paratype.com/fonts/pt/pt-astra-serif

@calixteman
Copy link
Contributor

/botio test

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Received

Command cmd_test from @calixteman received. Current queue size: 0

Live output at: http://54.241.84.105:8877/9919e5c49c0afa0/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Received

Command cmd_test from @calixteman received. Current queue size: 0

Live output at: http://54.193.163.58:8877/cac78d3ee45096e/output.txt

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Linux m4)


Failed

Full output at http://54.241.84.105:8877/9919e5c49c0afa0/output.txt

Total script time: 38.95 mins

  • Unit tests: Passed
  • Integration Tests: Passed
  • Regression tests: FAILED
  different ref/snapshot: 269

Image differences available at: http://54.241.84.105:8877/9919e5c49c0afa0/reftest-analyzer.html#web=eq.log

@moz-tools-bot
Copy link
Collaborator

From: Bot.io (Windows)


Failed

Full output at http://54.193.163.58:8877/cac78d3ee45096e/output.txt

Total script time: 78.04 mins

  • Unit tests: FAILED
  • Integration Tests: Passed
  • Regression tests: FAILED
  different ref/snapshot: 258

Image differences available at: http://54.193.163.58:8877/cac78d3ee45096e/reftest-analyzer.html#web=eq.log

@CoelacanthusHex
Copy link
Author

CoelacanthusHex commented Oct 25, 2025

Looks like all test failures are about a different font grayscale antialias. And many of them don't even use 'Times Roman'. I have no idea about the relation between failure and my change (Just add a new font to 'Times Roman' fallback list.).

@timvandermeij
Copy link
Contributor

timvandermeij commented Oct 26, 2025

The reference test failures are not related to your patch. The reason for the differences is that Firefox Nightly got updated on the bots a few days ago, which ever so slightly changed font rendering for some PDF files. To fix this we just have to regenerate the reference test images with the new version, which is being done over at #20397. Once that's done we can re-run the tests here.

In the meantime, could you perhaps add a test case (PDF file) to this PR that serves as a regression test to make sure that the font substitution works, and keeps working, as expected? A simple one-page PDF file with some text in this font (probably without embedding the font) will suffice. You can look at https://github.com/mozilla/pdf.js/pull/20270/files as an example of how to do this: basically it involves adding the PDF file itself, updating .gitignore and including it as an equality test in the test manifest.

Thank you!

@CoelacanthusHex CoelacanthusHex force-pushed the feat/pt-astra-serif branch 2 times, most recently from f57fce4 to 624bb2c Compare October 27, 2025 06:26
@CoelacanthusHex
Copy link
Author

In the meantime, could you perhaps add a test case (PDF file) to this PR that serves as a regression test to make sure that the font substitution works, and keeps working, as expected? A simple one-page PDF file with some text in this font (probably without embedding the font) will suffice. You can look at #20270 (files)

Ok. I added a new test PDF, which used PT Astra Serif and without embedded it.

…Roman

Metric-compatible font with Times New Roman created by ParaType, based on
their serif font PT Serif, released under OFL-1.1 license.

https://www.paratype.com/fonts/pt/pt-astra-serif

Signed-off-by: Coelacanthus <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants